You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
FOUR-6787 If more than two tasks end in an Intermediate Signal Throw Event Element, the flow will not be correctly completed - #9099
If more than two tasks end in an Intermediate Signal Throw Event Element, the flow will not be correctly completed
An Intermediate Throw Event with two or more incoming sequence flows behaved like an AND-join. TransitionTrait::hasAllRequiredTokens only fired the shared transition when every incoming state had a token, and one firing consumed one token from each incoming flow. When an exclusive or parallel split delivered a token on only some of those flows, the event never fired and the request stayed In Progress.
The event is no longer a join. IntermediateThrowEventTransition fires as soon as any incoming flow has a token and consumes exactly one token per firing, so each arriving token triggers the event and continues downstream. The graph is unchanged: one incoming state per sequence flow, all connected to the same transition. Token persistence and ThrowEventTokenPassed still happen on that transition, which keeps the previous event order for boundary and message tests.
Before this change the transition waited until inA, inB, and inC all held a token. Now a token on any one of them is enough.
Low Risk
Adds tests and a fixture only; no application or workflow engine code changes in this diff.
Overview
Adds integration coverage for FOUR-6787 so an Intermediate Message Throw Event with several incoming sequence flows does not behave like an AND-join after the Nayra workflow fix.
A new process fixture (four_6787_intermediate_throw_event.json) models an exclusive gateway with three branches that all converge on node_19, then end at a message end event. IntermediateThrowEventMergeTest imports that process, starts a request, picks each branch via select (1, 2, or 3), completes the branch form task, and asserts the request reaches COMPLETED.
Reviewed by Cursor Bugbot for commit d30cef1. Bugbot is set up for automated code reviews on this repo. Configure here.
devmiguelangel
changed the title
test: add tests for Intermediate Message Throw Event behavior
FOUR-6787 If more than two tasks end in an Intermediate Signal Throw Event Element, the flow will not be correctly completed- #240
Oct 13, 2026
devmiguelangel
changed the title
FOUR-6787 If more than two tasks end in an Intermediate Signal Throw Event Element, the flow will not be correctly completed- #240
FOUR-6787 If more than two tasks end in an Intermediate Signal Throw Event Element, the flow will not be correctly completed
Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
If more than two tasks end in an Intermediate Signal Throw Event Element, the flow will not be correctly completed
An Intermediate Throw Event with two or more incoming sequence flows behaved like an AND-join. TransitionTrait::hasAllRequiredTokens only fired the shared transition when every incoming state had a token, and one firing consumed one token from each incoming flow. When an exclusive or parallel split delivered a token on only some of those flows, the event never fired and the request stayed In Progress.
The event is no longer a join. IntermediateThrowEventTransition fires as soon as any incoming flow has a token and consumes exactly one token per firing, so each arriving token triggers the event and continues downstream. The graph is unchanged: one incoming state per sequence flow, all connected to the same transition. Token persistence and ThrowEventTokenPassed still happen on that transition, which keeps the previous event order for boundary and message tests.
Before this change the transition waited until inA, inB, and inC all held a token. Now a token on any one of them is enough.
Related Tickets
FOUR-6787
ProcessMaker/nayra#240
ci:nayra:FOUR-6787
ci:deploy